Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 810ac161fe52f695c0e6dd4c207ecdff4344b66dfbcdb23e1ade96d8f430a621

Tx prefix hash: efee4402cb3404a5f278a3ab71bc5e8a2868bdd061941de402068defd135a0e3
Tx public key: 00d882ea1a52dce1f94cb630173040ab2eae851b2ee32bc6fc3c889446366fa9
Timestamp: 1736991335 Timestamp [UCT]: 2025-01-16 01:35:35 Age [y:d:h:m:s]: 00:334:22:57:44
Block: 1198274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236942 RingCT/type: yes/0
Extra: 0100d882ea1a52dce1f94cb630173040ab2eae851b2ee32bc6fc3c889446366fa9021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74ecd277862811cbda2a4509494d3e6e919216dbff5eadc55945020b84dd30c8 0.600000000000 1684895 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": 1198284, "vin": [ { "gen": { "height": 1198274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74ecd277862811cbda2a4509494d3e6e919216dbff5eadc55945020b84dd30c8" } } ], "extra": [ 1, 0, 216, 130, 234, 26, 82, 220, 225, 249, 76, 182, 48, 23, 48, 64, 171, 46, 174, 133, 27, 46, 227, 43, 198, 252, 60, 136, 148, 70, 54, 111, 169, 2, 17, 0, 0, 0, 9, 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