Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 525953fc819e3f1f71a3db31f5f606c4cf00d1860d6cb66d856b9dd3b5d0ed28

Tx prefix hash: c422ae9e2eb4062aa9040ee7aaef63c5ab5bc6deb652a0b913d37473c1da6031
Tx public key: 567c75e5ef7c22809c352448d51430479ea802abebc8f6652c554f1e4596a186
Timestamp: 1672983223 Timestamp [UCT]: 2023-01-06 05:33:43 Age [y:d:h:m:s]: 02:108:22:36:51
Block: 668631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599553 RingCT/type: yes/0
Extra: 01567c75e5ef7c22809c352448d51430479ea802abebc8f6652c554f1e4596a18602110000000733af99f4000000000000000000

1 output(s) for total of 3.737213374000 dcy

stealth address amount amount idx
00: 5ecb70fa8961205731f57318b8f6ece4bfdf033c85d378e195444541291b38f4 3.737213374000 1109888 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": 668641, "vin": [ { "gen": { "height": 668631 } } ], "vout": [ { "amount": 3737213374, "target": { "key": "5ecb70fa8961205731f57318b8f6ece4bfdf033c85d378e195444541291b38f4" } } ], "extra": [ 1, 86, 124, 117, 229, 239, 124, 34, 128, 156, 53, 36, 72, 213, 20, 48, 71, 158, 168, 2, 171, 235, 200, 246, 101, 44, 85, 79, 30, 69, 150, 161, 134, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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