Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7713edaee0a99261d4f30ee16c4edc6eb7a208b163e07f4f4bad080f6b858d74

Tx prefix hash: 95a951bb6162915a023e28b9015b9bff8d24cc1f0d2fe196cae87429816a66fe
Tx public key: 0fb7cd61238a385f2d6c0fbd340da2d0fe40c1b75e894567ba6af1c08571d4fd
Timestamp: 1714105057 Timestamp [UCT]: 2024-04-26 04:17:37 Age [y:d:h:m:s]: 00:250:10:46:27
Block: 1008676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179273 RingCT/type: yes/0
Extra: 010fb7cd61238a385f2d6c0fbd340da2d0fe40c1b75e894567ba6af1c08571d4fd02110000000118ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f6efdaec6fdee65acd6c7482e5b1a0238fce88e5cf3e2e4499fca1e2387a3d4 0.600000000000 1470152 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": 1008686, "vin": [ { "gen": { "height": 1008676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f6efdaec6fdee65acd6c7482e5b1a0238fce88e5cf3e2e4499fca1e2387a3d4" } } ], "extra": [ 1, 15, 183, 205, 97, 35, 138, 56, 95, 45, 108, 15, 189, 52, 13, 162, 208, 254, 64, 193, 183, 94, 137, 69, 103, 186, 106, 241, 192, 133, 113, 212, 253, 2, 17, 0, 0, 0, 1, 24, 236, 144, 96, 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