Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba4f7c5451d5757d4f5f7338fe89bc67c8a0b21a1fa290f77967e6057d8401a

Tx prefix hash: 91fb0f793c9c9813885b315347a7c7a9debf52e686ab32d9b50bb642d855d888
Tx public key: e883e85cbd4aded9facb10d41b3f3e596d4df9b42313627b2f5992033718bc2d
Timestamp: 1734546688 Timestamp [UCT]: 2024-12-18 18:31:28 Age [y:d:h:m:s]: 00:184:10:15:08
Block: 1178066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131452 RingCT/type: yes/0
Extra: 01e883e85cbd4aded9facb10d41b3f3e596d4df9b42313627b2f5992033718bc2d02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf7265dfd61ea43621282a143e171f37062fa4aac11ec44fb30195530ee0941 0.600000000000 1664449 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": 1178076, "vin": [ { "gen": { "height": 1178066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf7265dfd61ea43621282a143e171f37062fa4aac11ec44fb30195530ee0941" } } ], "extra": [ 1, 232, 131, 232, 92, 189, 74, 222, 217, 250, 203, 16, 212, 27, 63, 62, 89, 109, 77, 249, 180, 35, 19, 98, 123, 47, 89, 146, 3, 55, 24, 188, 45, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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