Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1a3fb255d89aed3fdfcc9cab3ac4b0abfb58a4fc35e1eb5089bb6846221bbb

Tx prefix hash: e00bf0b572f7973091123e889d76b827191f10a6df95c6966f29709d99d314f3
Tx public key: f897e2681cc5ddeaf3e4f39698628b44aba28dcf037fde2ae51d101065f98c86
Timestamp: 1718483653 Timestamp [UCT]: 2024-06-15 20:34:13 Age [y:d:h:m:s]: 00:279:07:12:42
Block: 1044998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199568 RingCT/type: yes/0
Extra: 01f897e2681cc5ddeaf3e4f39698628b44aba28dcf037fde2ae51d101065f98c86021100000001b27e313d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d7533368f786c836c4c5867e2b54308c2a80739f2d3bddba8e3a183d1964f7a 0.600000000000 1514453 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": 1045008, "vin": [ { "gen": { "height": 1044998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d7533368f786c836c4c5867e2b54308c2a80739f2d3bddba8e3a183d1964f7a" } } ], "extra": [ 1, 248, 151, 226, 104, 28, 197, 221, 234, 243, 228, 243, 150, 152, 98, 139, 68, 171, 162, 141, 207, 3, 127, 222, 42, 229, 29, 16, 16, 101, 249, 140, 134, 2, 17, 0, 0, 0, 1, 178, 126, 49, 61, 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