Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ea7b5554fd1b7b051c66f5cd576fa893d1281db905ffb2bfc6292697b3720aa

Tx prefix hash: 04745f91e1d726aaa528c04f04fecfecddd15759c6f3b41e7794c960190b4865
Tx public key: f2ca6264d74352751b6914b1219c64bcfeda22e3a28aa41f34c2a0d2d8caec5d
Timestamp: 1708674410 Timestamp [UCT]: 2024-02-23 07:46:50 Age [y:d:h:m:s]: 01:028:22:11:57
Block: 963660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281694 RingCT/type: yes/0
Extra: 01f2ca6264d74352751b6914b1219c64bcfeda22e3a28aa41f34c2a0d2d8caec5d021100000003105b1226000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef45ccf4699705de4e8e7d6fc52bf06c14662567ec401fd72733949bd2880b3b 0.600000000000 1423377 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": 963670, "vin": [ { "gen": { "height": 963660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef45ccf4699705de4e8e7d6fc52bf06c14662567ec401fd72733949bd2880b3b" } } ], "extra": [ 1, 242, 202, 98, 100, 215, 67, 82, 117, 27, 105, 20, 177, 33, 156, 100, 188, 254, 218, 34, 227, 162, 138, 164, 31, 52, 194, 160, 210, 216, 202, 236, 93, 2, 17, 0, 0, 0, 3, 16, 91, 18, 38, 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