Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7321b3987396e4a197bd32c1bd5fdff018f72e92897bb536b3d524a41151090

Tx prefix hash: 56c39dd537b554dd509870f730c1d5509d6d42aea883338c3343e71032d0adb7
Tx public key: f654c8e5ec630db4acd89ee93a4950e5df80639f327cea918775360e21007b98
Timestamp: 1632645826 Timestamp [UCT]: 2021-09-26 08:43:46 Age [y:d:h:m:s]: 03:230:07:18:23
Block: 341155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 940974 RingCT/type: yes/0
Extra: 01f654c8e5ec630db4acd89ee93a4950e5df80639f327cea918775360e21007b980211000000658d0de867000000000000000000

1 output(s) for total of 45.458996304000 dcy

stealth address amount amount idx
00: 6b29250ed4ec1a538821e3668afd3464ae792ee42e4694cafcd4c7ea22b34a6a 45.458996304000 700930 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": 341165, "vin": [ { "gen": { "height": 341155 } } ], "vout": [ { "amount": 45458996304, "target": { "key": "6b29250ed4ec1a538821e3668afd3464ae792ee42e4694cafcd4c7ea22b34a6a" } } ], "extra": [ 1, 246, 84, 200, 229, 236, 99, 13, 180, 172, 216, 158, 233, 58, 73, 80, 229, 223, 128, 99, 159, 50, 124, 234, 145, 135, 117, 54, 14, 33, 0, 123, 152, 2, 17, 0, 0, 0, 101, 141, 13, 232, 103, 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