Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1032464b85993e457625cf952e2d5f4d639f8e0330248668d954f24c6c1c1da8

Tx prefix hash: 040a33e753f7d7d6cee26c8ce8de43ff3e01915e100e6669a4529fdcba7f218b
Tx public key: b0b188918b15a76b947c2cfe2e624b5af371545f69f8269401de5868defafdae
Timestamp: 1698561353 Timestamp [UCT]: 2023-10-29 06:35:53 Age [y:d:h:m:s]: 02:011:11:10:06
Block: 880034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527771 RingCT/type: yes/0
Extra: 01b0b188918b15a76b947c2cfe2e624b5af371545f69f8269401de5868defafdae02110000001075e3f0e9000000000000000000

1 output(s) for total of 0.744872689000 dcy

stealth address amount amount idx
00: f12b56ed56e9922fd5e4fb3024e4c9db8cd42994859cc15eaef0c86c05c819ef 0.744872689000 1335576 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": 880044, "vin": [ { "gen": { "height": 880034 } } ], "vout": [ { "amount": 744872689, "target": { "key": "f12b56ed56e9922fd5e4fb3024e4c9db8cd42994859cc15eaef0c86c05c819ef" } } ], "extra": [ 1, 176, 177, 136, 145, 139, 21, 167, 107, 148, 124, 44, 254, 46, 98, 75, 90, 243, 113, 84, 95, 105, 248, 38, 148, 1, 222, 88, 104, 222, 250, 253, 174, 2, 17, 0, 0, 0, 16, 117, 227, 240, 233, 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