Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb4f1407d56dec817c170ea8cf502ffcaf32fc1b5610523fc82b30e2a62cf33

Tx prefix hash: 03663e2266a82a6c50f6a44d35af0c061b26b33611dfe023ae2f7b673cf32e92
Tx public key: a1f34073f6484261c131a7e0d7377139e7320dde83b9086ff5f330f448bd6bf4
Timestamp: 1695737011 Timestamp [UCT]: 2023-09-26 14:03:31 Age [y:d:h:m:s]: 01:253:14:18:05
Block: 856601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442348 RingCT/type: yes/0
Extra: 01a1f34073f6484261c131a7e0d7377139e7320dde83b9086ff5f330f448bd6bf40211000000034b8f5122000000000000000000

1 output(s) for total of 0.890687468000 dcy

stealth address amount amount idx
00: aac6b2d6eac040da454198e4860c353ab8f652e13645e813ae2eebfe6e7a1304 0.890687468000 1310681 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": 856611, "vin": [ { "gen": { "height": 856601 } } ], "vout": [ { "amount": 890687468, "target": { "key": "aac6b2d6eac040da454198e4860c353ab8f652e13645e813ae2eebfe6e7a1304" } } ], "extra": [ 1, 161, 243, 64, 115, 246, 72, 66, 97, 193, 49, 167, 224, 215, 55, 113, 57, 231, 50, 13, 222, 131, 185, 8, 111, 245, 243, 48, 244, 72, 189, 107, 244, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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