Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826a98c772ae06151f7afda24633f14a277a28b6f4fa99ef554f989c2ddb8b7e

Tx prefix hash: eff6102d2736b22ce65954498d37e31f5c4606ab4e535860272db59bbd62026b
Tx public key: 52d2af7cf65c2236df0b9c73b2147697a69cd9679b351d5f44ca16a85f4fe3c6
Timestamp: 1727968156 Timestamp [UCT]: 2024-10-03 15:09:16 Age [y:d:h:m:s]: 00:223:02:49:47
Block: 1123623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159292 RingCT/type: yes/0
Extra: 0152d2af7cf65c2236df0b9c73b2147697a69cd9679b351d5f44ca16a85f4fe3c602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4383bae93331720180e5e794b57b620e9c18bb66ab7273cefb717d8ce447b625 0.600000000000 1606158 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": 1123633, "vin": [ { "gen": { "height": 1123623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4383bae93331720180e5e794b57b620e9c18bb66ab7273cefb717d8ce447b625" } } ], "extra": [ 1, 82, 210, 175, 124, 246, 92, 34, 54, 223, 11, 156, 115, 178, 20, 118, 151, 166, 156, 217, 103, 155, 53, 29, 95, 68, 202, 22, 168, 95, 79, 227, 198, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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