Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2c86b716f83a34d363b40e6c0a9d3b33cb80220fb4da82091e6f17199ee0d940

Tx prefix hash: c09175f2f5677b10f303daf2a0326ebc88536db0227a884091f49b92eec03bdb
Tx public key: 80bbb4660796b1ca8b44bf672f88be98e920e70e1716a0f82c5328381f4220d5
Timestamp: 1725260749 Timestamp [UCT]: 2024-09-02 07:05:49 Age [y:d:h:m:s]: 00:212:20:15:11
Block: 1101166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151961 RingCT/type: yes/0
Extra: 0180bbb4660796b1ca8b44bf672f88be98e920e70e1716a0f82c5328381f4220d502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c95a93c6b300f7cd3956c9931489b5eb78c408373cb269e1e0ee9d4760279b98 0.600000000000 1577151 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1101176, "vin": [ { "gen": { "height": 1101166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c95a93c6b300f7cd3956c9931489b5eb78c408373cb269e1e0ee9d4760279b98" } } ], "extra": [ 1, 128, 187, 180, 102, 7, 150, 177, 202, 139, 68, 191, 103, 47, 136, 190, 152, 233, 32, 231, 14, 23, 22, 160, 248, 44, 83, 40, 56, 31, 66, 32, 213, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8