Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3e8fd9954777488df4e3310b4a9edb8d89b0cbfb596b7eadf23d1dbd2f022d0

Tx prefix hash: 41d066a54dd535bdb585ee683f08986f2adbf64ed99ffe3b4e20fe0469e3ce1c
Tx public key: 6b745e704ffc5ca7f626664ad40aa1cfa45381e097c6bc9136a75223a81f56ce
Timestamp: 1578799556 Timestamp [UCT]: 2020-01-12 03:25:56 Age [y:d:h:m:s]: 05:055:01:00:39
Block: 43610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189536 RingCT/type: yes/0
Extra: 016b745e704ffc5ca7f626664ad40aa1cfa45381e097c6bc9136a75223a81f56ce021100000073dcee4b4d000000000000000000

1 output(s) for total of 440.050794030000 dcy

stealth address amount amount idx
00: 0a7fe212725b6cb0d8a786a4cc812f30ef5f9de163e0ee122dd17e158d27dc97 440.050794030000 79063 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": 43620, "vin": [ { "gen": { "height": 43610 } } ], "vout": [ { "amount": 440050794030, "target": { "key": "0a7fe212725b6cb0d8a786a4cc812f30ef5f9de163e0ee122dd17e158d27dc97" } } ], "extra": [ 1, 107, 116, 94, 112, 79, 252, 92, 167, 246, 38, 102, 74, 212, 10, 161, 207, 164, 83, 129, 224, 151, 198, 188, 145, 54, 167, 82, 35, 168, 31, 86, 206, 2, 17, 0, 0, 0, 115, 220, 238, 75, 77, 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