Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbc13990f691c7b2d4fb2c826d64d98eb2f391bd2f8d34db36691cb6f022609

Tx prefix hash: 5d34970420f0aff8606faddf49b8b7dae335e6f1d057ca83b0712bdc0deb26c3
Tx public key: 68fc674e10b08bf494cd37e7a9e93212fd29f2d0794358fd28f910883aa87721
Timestamp: 1716432467 Timestamp [UCT]: 2024-05-23 02:47:47 Age [y:d:h:m:s]: 00:319:18:40:50
Block: 1027981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228542 RingCT/type: yes/0
Extra: 0168fc674e10b08bf494cd37e7a9e93212fd29f2d0794358fd28f910883aa8772102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe9c68f4ee4414bdbcf913fac50c05e7fd0d2ba3d09fcf76e26eabe86c7bad22 0.600000000000 1495872 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": 1027991, "vin": [ { "gen": { "height": 1027981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe9c68f4ee4414bdbcf913fac50c05e7fd0d2ba3d09fcf76e26eabe86c7bad22" } } ], "extra": [ 1, 104, 252, 103, 78, 16, 176, 139, 244, 148, 205, 55, 231, 169, 233, 50, 18, 253, 41, 242, 208, 121, 67, 88, 253, 40, 249, 16, 136, 58, 168, 119, 33, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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