Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4295ef36a30c448648a9626f81027fe37795786df575ab1f7c5bdda894210b

Tx prefix hash: 451a67010161b3a097d503d7d9c8c5d7692c83ccf2670e01fc5b0b127920b059
Tx public key: 3088d848f02803ae17d331f849e65e1dce46280218c9a363f4f28cfa19a8daa0
Timestamp: 1720533171 Timestamp [UCT]: 2024-07-09 13:52:51 Age [y:d:h:m:s]: 00:343:22:30:05
Block: 1061979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245677 RingCT/type: yes/0
Extra: 013088d848f02803ae17d331f849e65e1dce46280218c9a363f4f28cfa19a8daa002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a9e6071bbe6aa7861c70d3db08aff0e6f1e8c3167580ca97fe6839409e8e3e 0.600000000000 1532478 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": 1061989, "vin": [ { "gen": { "height": 1061979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a9e6071bbe6aa7861c70d3db08aff0e6f1e8c3167580ca97fe6839409e8e3e" } } ], "extra": [ 1, 48, 136, 216, 72, 240, 40, 3, 174, 23, 211, 49, 248, 73, 230, 94, 29, 206, 70, 40, 2, 24, 201, 163, 99, 244, 242, 140, 250, 25, 168, 218, 160, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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