Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bbb105d8e4436ce23240ec1a1e375c9aeb3673d2f7b4fc275d9872e88c72094

Tx prefix hash: 266aa1273946c95b19dd1a531acaa3fb5409f95e720519cc58bfe0fc668c2fb8
Tx public key: 8d72cf721ae3efbc26210039a0f914bb74249d44169379d526f6a4774af0282f
Timestamp: 1745764675 Timestamp [UCT]: 2025-04-27 14:37:55 Age [y:d:h:m:s]: 00:208:03:06:03
Block: 1270642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146458 RingCT/type: yes/0
Extra: 018d72cf721ae3efbc26210039a0f914bb74249d44169379d526f6a4774af0282f0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5276cb7116a46b23c7a8ba814d0ec9d97c18a87489ab3152fc424c72e15e2ed9 0.600000000000 1757885 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": 1270652, "vin": [ { "gen": { "height": 1270642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5276cb7116a46b23c7a8ba814d0ec9d97c18a87489ab3152fc424c72e15e2ed9" } } ], "extra": [ 1, 141, 114, 207, 114, 26, 227, 239, 188, 38, 33, 0, 57, 160, 249, 20, 187, 116, 36, 157, 68, 22, 147, 121, 213, 38, 246, 164, 119, 74, 240, 40, 47, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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