Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf910e04e57e9d4a20817cf0a9e0db37023ec17281086a7328f57fce3e27fbb2

Tx prefix hash: 7ac5210977a9c76e9a87a3f744a4205cf06185ed2223abf3d000f94d30e04b49
Tx public key: e34917ebaa61d5afaa8fcb8f364d2a782d15b7e265669f5d0aa7a6ea319d80de
Timestamp: 1737391259 Timestamp [UCT]: 2025-01-20 16:40:59 Age [y:d:h:m:s]: 00:148:09:38:55
Block: 1201538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105817 RingCT/type: yes/0
Extra: 01e34917ebaa61d5afaa8fcb8f364d2a782d15b7e265669f5d0aa7a6ea319d80de02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c5a1d7f091f69f21ac36b62ee4e3a47c0ca2ad83d30aca5ba24c00484893408 0.600000000000 1688191 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": 1201548, "vin": [ { "gen": { "height": 1201538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c5a1d7f091f69f21ac36b62ee4e3a47c0ca2ad83d30aca5ba24c00484893408" } } ], "extra": [ 1, 227, 73, 23, 235, 170, 97, 213, 175, 170, 143, 203, 143, 54, 77, 42, 120, 45, 21, 183, 226, 101, 102, 159, 93, 10, 167, 166, 234, 49, 157, 128, 222, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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