Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe9d88de7175d19186e6f2feba7612499068a9c43dfe56f0265f3e6fbfb217c

Tx prefix hash: ee404ae80c0ba1abb958e2578de9c8e3dd118c689fa35d0febd2b2ea871dffd6
Tx public key: 415865e4416e2b291d07a9013eeefe0237c7d2228fcfc5440a4594bfcded379d
Timestamp: 1704764437 Timestamp [UCT]: 2024-01-09 01:40:37 Age [y:d:h:m:s]: 01:302:10:12:30
Block: 931227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474952 RingCT/type: yes/0
Extra: 01415865e4416e2b291d07a9013eeefe0237c7d2228fcfc5440a4594bfcded379d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26477a8be95dc83ed177bc7de3fb08d53c3a0040c37a8943581d7af1bf0876b4 0.600000000000 1389123 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": 931237, "vin": [ { "gen": { "height": 931227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26477a8be95dc83ed177bc7de3fb08d53c3a0040c37a8943581d7af1bf0876b4" } } ], "extra": [ 1, 65, 88, 101, 228, 65, 110, 43, 41, 29, 7, 169, 1, 62, 238, 254, 2, 55, 199, 210, 34, 143, 207, 197, 68, 10, 69, 148, 191, 205, 237, 55, 157, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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