Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13c30d6c9c53c70fbad45a19aae0502e9c516d85a5534c4e1735a34539974dca

Tx prefix hash: f8c5b706c3ade9b3a30a8fbb85d03f483cb5af677cb25055d4b060c714ac7d46
Tx public key: 032bfb03abcbdcfc94e5d352b9302276ca033d286de575edfef840a740c4dce8
Timestamp: 1608915576 Timestamp [UCT]: 2020-12-25 16:59:36 Age [y:d:h:m:s]: 04:001:16:18:52
Block: 169274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1014219 RingCT/type: yes/0
Extra: 01032bfb03abcbdcfc94e5d352b9302276ca033d286de575edfef840a740c4dce80211000000ca90ce5c0f000000000000000000

1 output(s) for total of 168.704099431000 dcy

stealth address amount amount idx
00: c3c52b22b571d77b4fc82295dde0aac34defb912fb6e1b06e28ec728c8c73d1b 168.704099431000 315645 of 0

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": 169284, "vin": [ { "gen": { "height": 169274 } } ], "vout": [ { "amount": 168704099431, "target": { "key": "c3c52b22b571d77b4fc82295dde0aac34defb912fb6e1b06e28ec728c8c73d1b" } } ], "extra": [ 1, 3, 43, 251, 3, 171, 203, 220, 252, 148, 229, 211, 82, 185, 48, 34, 118, 202, 3, 61, 40, 109, 229, 117, 237, 254, 248, 64, 167, 64, 196, 220, 232, 2, 17, 0, 0, 0, 202, 144, 206, 92, 15, 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