Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b71bf14a0b9255d24223a08e3e8743c63f3f7a60ae34508269c8370b006ecfa1

Tx prefix hash: 987ac7a1087303e092ffb52640c7a41aa28e59d75fb299789d6269f0caefcdaf
Tx public key: fc169c3249d51abb212945de6cb2275ebce43638a47ac0d08ecf10df71530873
Timestamp: 1720187090 Timestamp [UCT]: 2024-07-05 13:44:50 Age [y:d:h:m:s]: 01:137:20:21:35
Block: 1059099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357058 RingCT/type: yes/0
Extra: 01fc169c3249d51abb212945de6cb2275ebce43638a47ac0d08ecf10df715308730211000000038fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ca11a3aa74e9f9882f55f7d5437a8f8bdb17f8fdf79a3a3dc78460a36e3596f 0.600000000000 1529560 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": 1059109, "vin": [ { "gen": { "height": 1059099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ca11a3aa74e9f9882f55f7d5437a8f8bdb17f8fdf79a3a3dc78460a36e3596f" } } ], "extra": [ 1, 252, 22, 156, 50, 73, 213, 26, 187, 33, 41, 69, 222, 108, 178, 39, 94, 188, 228, 54, 56, 164, 122, 192, 208, 142, 207, 16, 223, 113, 83, 8, 115, 2, 17, 0, 0, 0, 3, 143, 218, 155, 45, 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