Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbbd499944fa391efc45d53a5d9dc078222da88f1a6f3d09cd0d41900244765a

Tx prefix hash: fa64675034d71be043427c9b45e186192b2369adfc611cc24a147c34fcfc23dd
Tx public key: db62b1ae7b68c20f89651599f8fb6493f0cbb4e48589262778c2d3defbc577d3
Timestamp: 1579437219 Timestamp [UCT]: 2020-01-19 12:33:39 Age [y:d:h:m:s]: 04:342:20:20:21
Block: 48945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134533 RingCT/type: yes/0
Extra: 01db62b1ae7b68c20f89651599f8fb6493f0cbb4e48589262778c2d3defbc577d3021100000001dcee4b4d000000000000000000

1 output(s) for total of 422.499044871000 dcy

stealth address amount amount idx
00: ac054d8454acf57f7a26472015a88c349093c8ecbfb5043c410a6198aadf87cb 422.499044871000 90787 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": 48955, "vin": [ { "gen": { "height": 48945 } } ], "vout": [ { "amount": 422499044871, "target": { "key": "ac054d8454acf57f7a26472015a88c349093c8ecbfb5043c410a6198aadf87cb" } } ], "extra": [ 1, 219, 98, 177, 174, 123, 104, 194, 15, 137, 101, 21, 153, 248, 251, 100, 147, 240, 203, 180, 228, 133, 137, 38, 39, 120, 194, 211, 222, 251, 197, 119, 211, 2, 17, 0, 0, 0, 1, 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