Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14736725eae9387146a9badcee78cc66c56df8c0f3538475fdb5bd55624291d2

Tx prefix hash: 91e9ec1dbcc4d72d76a414328a1d685b995b8c1a22c9f9711ca2748dc881409f
Tx public key: 43e94623bd43e86c4da96fe4a946300a2d5e32242b063a85b853c1b62b33890f
Timestamp: 1702500300 Timestamp [UCT]: 2023-12-13 20:45:00 Age [y:d:h:m:s]: 01:126:13:28:09
Block: 912472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351602 RingCT/type: yes/0
Extra: 0143e94623bd43e86c4da96fe4a946300a2d5e32242b063a85b853c1b62b33890f02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b65176df3d437078b0945a76bbf28dfcb9750510c169a4373ecb446ed7cb23e 0.600000000000 1369700 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": 912482, "vin": [ { "gen": { "height": 912472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b65176df3d437078b0945a76bbf28dfcb9750510c169a4373ecb446ed7cb23e" } } ], "extra": [ 1, 67, 233, 70, 35, 189, 67, 232, 108, 77, 169, 111, 228, 169, 70, 48, 10, 45, 94, 50, 36, 43, 6, 58, 133, 184, 83, 193, 182, 43, 51, 137, 15, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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