Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866cc4c2e48560e0b29045cecf8da4bc1e6f70ac6dac07401ef9c8ab27fdd006

Tx prefix hash: 934e018c67e7f4212c943092d0f520f054cd7db062de18e77d44c82293a3ad37
Tx public key: 0d2ecbc1223f3ae81a034b3eb6d22b21f5daad021955c57547df712e08601773
Timestamp: 1698194166 Timestamp [UCT]: 2023-10-25 00:36:06 Age [y:d:h:m:s]: 01:090:00:28:40
Block: 876987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325524 RingCT/type: yes/0
Extra: 010d2ecbc1223f3ae81a034b3eb6d22b21f5daad021955c57547df712e0860177302110000000533af99f4000000000000000000

1 output(s) for total of 0.762391475000 dcy

stealth address amount amount idx
00: e1afccc8211aca343a775bdfa4da66bd0e0bec44642e7f95d9a7099979821ddc 0.762391475000 1332343 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": 876997, "vin": [ { "gen": { "height": 876987 } } ], "vout": [ { "amount": 762391475, "target": { "key": "e1afccc8211aca343a775bdfa4da66bd0e0bec44642e7f95d9a7099979821ddc" } } ], "extra": [ 1, 13, 46, 203, 193, 34, 63, 58, 232, 26, 3, 75, 62, 182, 210, 43, 33, 245, 218, 173, 2, 25, 85, 197, 117, 71, 223, 113, 46, 8, 96, 23, 115, 2, 17, 0, 0, 0, 5, 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