Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff8eabd9fb608a9b11e6f4a90633f2a9f578d54d8e86673d79ea3da1a94e01d

Tx prefix hash: a07de443e9df12c71cd3984570f4c5d12d0fe71f16c4af3d8e3b9680e9d9ba18
Tx public key: 648e0aec4ed72a8b5561e4592d5081f84d2b0d123b2a8542454f1e20a471f4c9
Timestamp: 1745156552 Timestamp [UCT]: 2025-04-20 13:42:32 Age [y:d:h:m:s]: 00:023:23:25:18
Block: 1265604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17168 RingCT/type: yes/0
Extra: 01648e0aec4ed72a8b5561e4592d5081f84d2b0d123b2a8542454f1e20a471f4c90211000000086c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 042c51910ff0a826a017f843197a08ab1fec9149abbbee6beace857a4adeb442 0.600000000000 1752817 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": 1265614, "vin": [ { "gen": { "height": 1265604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "042c51910ff0a826a017f843197a08ab1fec9149abbbee6beace857a4adeb442" } } ], "extra": [ 1, 100, 142, 10, 236, 78, 215, 42, 139, 85, 97, 228, 89, 45, 80, 129, 248, 77, 43, 13, 18, 59, 42, 133, 66, 69, 79, 30, 32, 164, 113, 244, 201, 2, 17, 0, 0, 0, 8, 108, 152, 170, 61, 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