Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a50f37bcff6b66d7c3dee421273e9bbf76c4ee616517f15d6f21535ba7f01d10

Tx prefix hash: 47870c9a93523acd52fa405a8bad88a8e129989cdbf266bc3715d87bc1e75e7e
Tx public key: b487aaeeb9aa54382c6f43e679538e4d8c2745a9bd02dd032dfa638a83ca93fd
Timestamp: 1705090409 Timestamp [UCT]: 2024-01-12 20:13:29 Age [y:d:h:m:s]: 01:075:22:42:03
Block: 933926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315386 RingCT/type: yes/0
Extra: 01b487aaeeb9aa54382c6f43e679538e4d8c2745a9bd02dd032dfa638a83ca93fd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa46412dd2a99a3017a6f6719006f2c8bfb97bde7cffedbb2eca4f5bb6eb27cc 0.600000000000 1391910 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": 933936, "vin": [ { "gen": { "height": 933926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa46412dd2a99a3017a6f6719006f2c8bfb97bde7cffedbb2eca4f5bb6eb27cc" } } ], "extra": [ 1, 180, 135, 170, 238, 185, 170, 84, 56, 44, 111, 67, 230, 121, 83, 142, 77, 140, 39, 69, 169, 189, 2, 221, 3, 45, 250, 99, 138, 131, 202, 147, 253, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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