Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce38b5e4e2b6c4828ffd8fc9dffd0db4e56268ca93f7f6c6228cf02f206a51b0

Tx prefix hash: 4a7c378a680c0358ac295582e037820ce050b6ba3eefbc33398fac86609ae2a7
Tx public key: 178f12338247693ed0195e9c33089d8f9f10cec9990c857d87704df68aa012a4
Timestamp: 1713554503 Timestamp [UCT]: 2024-04-19 19:21:43 Age [y:d:h:m:s]: 01:016:06:43:49
Block: 1004098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272601 RingCT/type: yes/0
Extra: 01178f12338247693ed0195e9c33089d8f9f10cec9990c857d87704df68aa012a402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384fa72b7d6e519a530950f3cc928de14c5e7201dcace0b3cbcc80b10ff12e2f 0.600000000000 1464664 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": 1004108, "vin": [ { "gen": { "height": 1004098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384fa72b7d6e519a530950f3cc928de14c5e7201dcace0b3cbcc80b10ff12e2f" } } ], "extra": [ 1, 23, 143, 18, 51, 130, 71, 105, 62, 208, 25, 94, 156, 51, 8, 157, 143, 159, 16, 206, 201, 153, 12, 133, 125, 135, 112, 77, 246, 138, 160, 18, 164, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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