Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3421c21d8db948ed0eea11c3cb31248a4079309518255407353b5b3c93d17504

Tx prefix hash: 2f0bf5f0f9ddf6d217e7a94ab051ef3de5a6203e95eb911c781bba7a1d6d07fe
Tx public key: 614161497ebf54382abdf29023d93e21b2cd29daf6ff098c1085d62972b14068
Timestamp: 1648567485 Timestamp [UCT]: 2022-03-29 15:24:45 Age [y:d:h:m:s]: 03:029:22:00:44
Block: 468977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801633 RingCT/type: yes/0
Extra: 01614161497ebf54382abdf29023d93e21b2cd29daf6ff098c1085d62972b14068021100000001cb8520c2000000000000000000

1 output(s) for total of 17.142918812000 dcy

stealth address amount amount idx
00: bec5a89fbfdcf94119f8cf70d0331ff710cfb27aa29b214ac3d399cfb2c3967c 17.142918812000 887815 of 0

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": 468987, "vin": [ { "gen": { "height": 468977 } } ], "vout": [ { "amount": 17142918812, "target": { "key": "bec5a89fbfdcf94119f8cf70d0331ff710cfb27aa29b214ac3d399cfb2c3967c" } } ], "extra": [ 1, 97, 65, 97, 73, 126, 191, 84, 56, 42, 189, 242, 144, 35, 217, 62, 33, 178, 205, 41, 218, 246, 255, 9, 140, 16, 133, 214, 41, 114, 177, 64, 104, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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