Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f12fe0eb47e065262a3899dff218cd8fe181409c93eafa615365c5e53c48ee91

Tx prefix hash: d46db3ec9be88fb4313801a3f95e1a6bb24ab03d430d4b26a4ed9f1a04e90719
Tx public key: a3f8adbdba7841efa142f7e8f5685f1e16d062401ccd79443959e2d7417eabf0
Timestamp: 1674775300 Timestamp [UCT]: 2023-01-26 23:21:40 Age [y:d:h:m:s]: 02:074:09:07:11
Block: 683495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574800 RingCT/type: yes/0
Extra: 01a3f8adbdba7841efa142f7e8f5685f1e16d062401ccd79443959e2d7417eabf0021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.336547179000 dcy

stealth address amount amount idx
00: e849f4d80205d90efd415c2983cd2cf31cf991604961be5f956957714ffc39a7 3.336547179000 1125686 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": 683505, "vin": [ { "gen": { "height": 683495 } } ], "vout": [ { "amount": 3336547179, "target": { "key": "e849f4d80205d90efd415c2983cd2cf31cf991604961be5f956957714ffc39a7" } } ], "extra": [ 1, 163, 248, 173, 189, 186, 120, 65, 239, 161, 66, 247, 232, 245, 104, 95, 30, 22, 208, 98, 64, 28, 205, 121, 68, 57, 89, 226, 215, 65, 126, 171, 240, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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