Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405331d808568d21be12fe96f79b446a684359f164d59531beefda01a57fdb76

Tx prefix hash: b462e84986ec0ad9096c8a5beb8832a8b303b496f1b7b4ab47782c2a81c4a7f1
Tx public key: 6fb94292d4a30d3dbf97a59da9b844a8094306dbfb067d0ce2d878411f351b31
Timestamp: 1723241522 Timestamp [UCT]: 2024-08-09 22:12:02 Age [y:d:h:m:s]: 00:234:11:37:46
Block: 1084425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167464 RingCT/type: yes/0
Extra: 016fb94292d4a30d3dbf97a59da9b844a8094306dbfb067d0ce2d878411f351b31021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434c0f236e879e767505d00873c183ab8ba01ddeeea4de6375e1dd76ab0b21ae 0.600000000000 1558698 of 15

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": 1084435, "vin": [ { "gen": { "height": 1084425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434c0f236e879e767505d00873c183ab8ba01ddeeea4de6375e1dd76ab0b21ae" } } ], "extra": [ 1, 111, 185, 66, 146, 212, 163, 13, 61, 191, 151, 165, 157, 169, 184, 68, 168, 9, 67, 6, 219, 251, 6, 125, 12, 226, 216, 120, 65, 31, 53, 27, 49, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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