Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a34faaa4ebf69408df54a7f6b1975da5dff80e8ae75937a1409af62239ee5a6

Tx prefix hash: 8495831ec3e408b5af1b7d3babea0e1439b88cc2f0b69cc6b4c8f392702aaf40
Tx public key: 2f835c973aab69b676ba9113dc6f0e4f9d0014dc74231c0be4f7005bf84fcb6d
Timestamp: 1737220550 Timestamp [UCT]: 2025-01-18 17:15:50 Age [y:d:h:m:s]: 00:151:03:09:39
Block: 1200135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107748 RingCT/type: yes/0
Extra: 012f835c973aab69b676ba9113dc6f0e4f9d0014dc74231c0be4f7005bf84fcb6d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4caea14ce8c165895ace7b009791d8ec2d7740f698e09e2780e60e8db7d3188e 0.600000000000 1686776 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": 1200145, "vin": [ { "gen": { "height": 1200135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4caea14ce8c165895ace7b009791d8ec2d7740f698e09e2780e60e8db7d3188e" } } ], "extra": [ 1, 47, 131, 92, 151, 58, 171, 105, 182, 118, 186, 145, 19, 220, 111, 14, 79, 157, 0, 20, 220, 116, 35, 28, 11, 228, 247, 0, 91, 248, 79, 203, 109, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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