Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 272e8f3a02c2eb7bb8cdddb1ed2ec7660837da417f2610270bdbf526247209f2

Tx prefix hash: 1b81728261de5e4f7cb4fca361192b6d26b6327659964d8710d8525b56bf8cc8
Tx public key: 2aa884a56271a9c9e89c6538c1fb037d175c6c490be7494d40ac41094430b1ca
Timestamp: 1722470908 Timestamp [UCT]: 2024-08-01 00:08:28 Age [y:d:h:m:s]: 00:301:17:57:40
Block: 1078035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215605 RingCT/type: yes/0
Extra: 012aa884a56271a9c9e89c6538c1fb037d175c6c490be7494d40ac41094430b1ca021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3ac10ebd2a406177e9c5dc176f3b4f739e118d4b9985f0a2a25d332677701cc 0.600000000000 1550590 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": 1078045, "vin": [ { "gen": { "height": 1078035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3ac10ebd2a406177e9c5dc176f3b4f739e118d4b9985f0a2a25d332677701cc" } } ], "extra": [ 1, 42, 168, 132, 165, 98, 113, 169, 201, 232, 156, 101, 56, 193, 251, 3, 125, 23, 92, 108, 73, 11, 231, 73, 77, 64, 172, 65, 9, 68, 48, 177, 202, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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