Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf27df6929ea9f68931c5f022f696825151923b9d873939a836a830c5ba885f1

Tx prefix hash: ed14e5a20a91d0146e4e0cea7458e1ddb3f4b97953fb4891f83f4b4b6c9288ce
Tx public key: 01a25d7912ea8adb2e21f990c91187bbeb98b945a44a1a3ec6db30cf0a2a22cf
Timestamp: 1632144311 Timestamp [UCT]: 2021-09-20 13:25:11 Age [y:d:h:m:s]: 03:096:15:56:57
Block: 337560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845098 RingCT/type: yes/0
Extra: 0101a25d7912ea8adb2e21f990c91187bbeb98b945a44a1a3ec6db30cf0a2a22cf02110000005a8d0de867000000000000000000

1 output(s) for total of 46.722280016000 dcy

stealth address amount amount idx
00: 4a3c39387a6d190fb491efb5cb11afdacb6646ab876c902e7ba8605d63977bef 46.722280016000 695037 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": 337570, "vin": [ { "gen": { "height": 337560 } } ], "vout": [ { "amount": 46722280016, "target": { "key": "4a3c39387a6d190fb491efb5cb11afdacb6646ab876c902e7ba8605d63977bef" } } ], "extra": [ 1, 1, 162, 93, 121, 18, 234, 138, 219, 46, 33, 249, 144, 201, 17, 135, 187, 235, 152, 185, 69, 164, 74, 26, 62, 198, 219, 48, 207, 10, 42, 34, 207, 2, 17, 0, 0, 0, 90, 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