Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f47fbfbf0704fe7ec9281c8372e24acd6efa4231d2845a1b84b6ee1db8501332

Tx prefix hash: 60054582c22d7675e77841d9f2ffabb43fec6112e67b71f9dd4727a62a28da1f
Tx public key: 8b7ff2689542d466f02a9f49b1362e72b7416ef30d7e7b81cef75e5c3e57bd59
Timestamp: 1713144046 Timestamp [UCT]: 2024-04-15 01:20:46 Age [y:d:h:m:s]: 00:315:16:39:39
Block: 1000694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225688 RingCT/type: yes/0
Extra: 018b7ff2689542d466f02a9f49b1362e72b7416ef30d7e7b81cef75e5c3e57bd5902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c35ff682524c8387eb83e2e04f89e5f523ed9a5fcb290cb7b7d936de793b64 0.600000000000 1461192 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": 1000704, "vin": [ { "gen": { "height": 1000694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c35ff682524c8387eb83e2e04f89e5f523ed9a5fcb290cb7b7d936de793b64" } } ], "extra": [ 1, 139, 127, 242, 104, 149, 66, 212, 102, 240, 42, 159, 73, 177, 54, 46, 114, 183, 65, 110, 243, 13, 126, 123, 129, 206, 247, 94, 92, 62, 87, 189, 89, 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