Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 482fd5ce0acb64176cf580c5f5737751ab6d17df7a643bb7cc51888c8b132ac0

Tx prefix hash: b54fa2ae68ae8fada4bc99abb2426793c36b86078e90fc440d8adaa4e805309a
Tx public key: af427aae54c92f11f94a1894aa408d2786a616184c4e3122b570227d4fd13f86
Timestamp: 1724134106 Timestamp [UCT]: 2024-08-20 06:08:26 Age [y:d:h:m:s]: 00:228:10:26:59
Block: 1091837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163127 RingCT/type: yes/0
Extra: 01af427aae54c92f11f94a1894aa408d2786a616184c4e3122b570227d4fd13f8602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baa0fe39a8cdf2e7f607f27f1f66b22b3255442528ed9dcf6685527980b1ffc0 0.600000000000 1566472 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": 1091847, "vin": [ { "gen": { "height": 1091837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baa0fe39a8cdf2e7f607f27f1f66b22b3255442528ed9dcf6685527980b1ffc0" } } ], "extra": [ 1, 175, 66, 122, 174, 84, 201, 47, 17, 249, 74, 24, 148, 170, 64, 141, 39, 134, 166, 22, 24, 76, 78, 49, 34, 181, 112, 34, 125, 79, 209, 63, 134, 2, 17, 0, 0, 0, 2, 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