Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2bf30e479a64f6a54758ef3a7ea6be98ae8f47d8bc0df804a686d93421274f4

Tx prefix hash: 441092c586f13ef44458361f257f71e0c7a99f7f409db8043ae0d4b5dbb61ab6
Tx public key: bbd729dfc0ed64249eab38d9f857bb3c3e319fcc54878b06a89a8457eaa6b7db
Timestamp: 1730808300 Timestamp [UCT]: 2024-11-05 12:05:00 Age [y:d:h:m:s]: 00:054:05:51:20
Block: 1147070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38811 RingCT/type: yes/0
Extra: 01bbd729dfc0ed64249eab38d9f857bb3c3e319fcc54878b06a89a8457eaa6b7db021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe80f13e6499d05eb0b0357e7d81c5e9b81f20df94014f64266469bb34e44f2 0.600000000000 1631763 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": 1147080, "vin": [ { "gen": { "height": 1147070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe80f13e6499d05eb0b0357e7d81c5e9b81f20df94014f64266469bb34e44f2" } } ], "extra": [ 1, 187, 215, 41, 223, 192, 237, 100, 36, 158, 171, 56, 217, 248, 87, 187, 60, 62, 49, 159, 204, 84, 135, 139, 6, 168, 154, 132, 87, 234, 166, 183, 219, 2, 17, 0, 0, 0, 4, 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