Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09aac28eab13cb838fd4d5b6e8f7c6c403119555d62213612d5b6c255baea4f9

Tx prefix hash: 67c2081fdbb7f1d85c21bcf9eafe21523451ce0ecfebb871a59fabcc0861ea18
Tx public key: 7ebb48880618c8de643555718d83aee18e974a3ed5708530c3fce67377c6b500
Timestamp: 1713443204 Timestamp [UCT]: 2024-04-18 12:26:44 Age [y:d:h:m:s]: 01:248:21:28:19
Block: 1003179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436604 RingCT/type: yes/0
Extra: 017ebb48880618c8de643555718d83aee18e974a3ed5708530c3fce67377c6b5000211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4ad24f24eea80c1e891c7999a717fe83d5042bb10cc8f2dfebe98b0c23f174 0.600000000000 1463709 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": 1003189, "vin": [ { "gen": { "height": 1003179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4ad24f24eea80c1e891c7999a717fe83d5042bb10cc8f2dfebe98b0c23f174" } } ], "extra": [ 1, 126, 187, 72, 136, 6, 24, 200, 222, 100, 53, 85, 113, 141, 131, 174, 225, 142, 151, 74, 62, 213, 112, 133, 48, 195, 252, 230, 115, 119, 198, 181, 0, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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