Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1ac6ef9071b11c344f787eb072e2718bac6df03828801fe5ace0419b95d8f0

Tx prefix hash: 36a5cc205af44a848ccbcf5da82dc0f161f903fa7d9884e45234e61e070dd54b
Tx public key: e3545c7ddc4ef3a22ff3161b5b4d0e7a07065bba34c2be85f1e51c6b43bfc604
Timestamp: 1671349575 Timestamp [UCT]: 2022-12-18 07:46:15 Age [y:d:h:m:s]: 02:166:16:35:48
Block: 655107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640877 RingCT/type: yes/0
Extra: 01e3545c7ddc4ef3a22ff3161b5b4d0e7a07065bba34c2be85f1e51c6b43bfc604021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.143416014000 dcy

stealth address amount amount idx
00: 0c3ddc7d42fd97f394fa0623583dc6743741df8f979acf75798fe8d574594d57 4.143416014000 1095652 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": 655117, "vin": [ { "gen": { "height": 655107 } } ], "vout": [ { "amount": 4143416014, "target": { "key": "0c3ddc7d42fd97f394fa0623583dc6743741df8f979acf75798fe8d574594d57" } } ], "extra": [ 1, 227, 84, 92, 125, 220, 78, 243, 162, 47, 243, 22, 27, 91, 77, 14, 122, 7, 6, 91, 186, 52, 194, 190, 133, 241, 229, 28, 107, 67, 191, 198, 4, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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