Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43bb7ea3c813a37abe33b731a06b8ab142fba253f95ce20694a172215349d63d

Tx prefix hash: 21881313f53d60a014b7ae7c28580f50ea7de2b1324961b506dda6fddf0db892
Tx public key: 0312b88aaa2b1c4be809e4f2d60876d54bfd3013e5b4cd73781a546490732cb8
Timestamp: 1703282627 Timestamp [UCT]: 2023-12-22 22:03:47 Age [y:d:h:m:s]: 01:142:05:38:07
Block: 918964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362790 RingCT/type: yes/0
Extra: 010312b88aaa2b1c4be809e4f2d60876d54bfd3013e5b4cd73781a546490732cb802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf2b9948523af0d57e4ed2c1f7adf3a56eedafdcdd063aa913cf3e02fc2b573f 0.600000000000 1376628 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": 918974, "vin": [ { "gen": { "height": 918964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf2b9948523af0d57e4ed2c1f7adf3a56eedafdcdd063aa913cf3e02fc2b573f" } } ], "extra": [ 1, 3, 18, 184, 138, 170, 43, 28, 75, 232, 9, 228, 242, 214, 8, 118, 213, 75, 253, 48, 19, 229, 180, 205, 115, 120, 26, 84, 100, 144, 115, 44, 184, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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