Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dab60c289d0cee5f3f67a0938a4c16fcc5cf426eaa4f810eb559f087017ee4a

Tx prefix hash: 0b16cc03fafc29b2974d9ff4e0920e707124b5d8c54910bc0f3d5260ec2f8368
Tx public key: b12794411ae12caeb2126cc08b55e88d982a35ae6d2d22dae39a0aca35bfc2e0
Timestamp: 1730409042 Timestamp [UCT]: 2024-10-31 21:10:42 Age [y:d:h:m:s]: 00:145:11:35:15
Block: 1143770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103794 RingCT/type: yes/0
Extra: 01b12794411ae12caeb2126cc08b55e88d982a35ae6d2d22dae39a0aca35bfc2e0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db71a30400d6954c5074f22b0eae7ca49d0ad0353f4cad3a07ca6b964f435b3b 0.600000000000 1627755 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": 1143780, "vin": [ { "gen": { "height": 1143770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db71a30400d6954c5074f22b0eae7ca49d0ad0353f4cad3a07ca6b964f435b3b" } } ], "extra": [ 1, 177, 39, 148, 65, 26, 225, 44, 174, 178, 18, 108, 192, 139, 85, 232, 141, 152, 42, 53, 174, 109, 45, 34, 218, 227, 154, 10, 202, 53, 191, 194, 224, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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