Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47fad0ae0cc325d1155f49275c77b9a5f1001ce0919354fbdcef8707a164cd95

Tx prefix hash: f983420d143d036bae22f5760524397ede64e32c7a7c2a2accf8f890cca2ae62
Tx public key: a1ee1bc030d158e506cfd50e50e4cc0ee6acb81e02202acd5f600fd1bfa7e818
Timestamp: 1716330994 Timestamp [UCT]: 2024-05-21 22:36:34 Age [y:d:h:m:s]: 00:186:20:24:28
Block: 1027139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133738 RingCT/type: yes/0
Extra: 01a1ee1bc030d158e506cfd50e50e4cc0ee6acb81e02202acd5f600fd1bfa7e81802110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 006ca08a1540d36ccdb96b518441e32b874a8de84c6dbd687a4df94f4dd65340 0.600000000000 1494606 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": 1027149, "vin": [ { "gen": { "height": 1027139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "006ca08a1540d36ccdb96b518441e32b874a8de84c6dbd687a4df94f4dd65340" } } ], "extra": [ 1, 161, 238, 27, 192, 48, 209, 88, 229, 6, 207, 213, 14, 80, 228, 204, 14, 230, 172, 184, 30, 2, 32, 42, 205, 95, 96, 15, 209, 191, 167, 232, 24, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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