Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 316d6e4c1cf0fcc2786a62cd8363c66749a1a85b7aa9415cfca61ba2188d0505

Tx prefix hash: 68ccad34163b1e3dceead6c289b989a7f38991579e99fc5c6b1573684cf589c8
Tx public key: e01e49b1325b272f4713776c434df8c60ec80a0a2131b2affc672e3ecc62d8fb
Timestamp: 1705340040 Timestamp [UCT]: 2024-01-15 17:34:00 Age [y:d:h:m:s]: 01:151:19:26:27
Block: 935999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369543 RingCT/type: yes/0
Extra: 01e01e49b1325b272f4713776c434df8c60ec80a0a2131b2affc672e3ecc62d8fb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9fc8e8530aa9fbbca45d19e7e61a93d563bc9da23cc1d3eb475cd43b259d68 0.600000000000 1394021 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": 936009, "vin": [ { "gen": { "height": 935999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9fc8e8530aa9fbbca45d19e7e61a93d563bc9da23cc1d3eb475cd43b259d68" } } ], "extra": [ 1, 224, 30, 73, 177, 50, 91, 39, 47, 71, 19, 119, 108, 67, 77, 248, 198, 14, 200, 10, 10, 33, 49, 178, 175, 252, 103, 46, 62, 204, 98, 216, 251, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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