Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e0024ff560f647ebfbe712a0c6c2e3274f2951542bf580fc1719a18434d87b9

Tx prefix hash: 58dd6986bed5bb8dd5f313d74fca994b1a2435673004b8b050c7cb4a00dcce73
Tx public key: 2eaaa8acc25b5381847b41ce273ac7a107e9da065ee3c9f45d36c8e69c765d0f
Timestamp: 1574362176 Timestamp [UCT]: 2019-11-21 18:49:36 Age [y:d:h:m:s]: 05:043:00:15:54
Block: 13861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1174204 RingCT/type: yes/0
Extra: 012eaaa8acc25b5381847b41ce273ac7a107e9da065ee3c9f45d36c8e69c765d0f02110000000166a80d00000000000000000000

1 output(s) for total of 552.171057312000 dcy

stealth address amount amount idx
00: cc4baeea9e1ccd76d06074d74d8c1b0b78a28a8e6179939b8e8fee925d12e4c5 552.171057312000 16902 of 0

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": 13871, "vin": [ { "gen": { "height": 13861 } } ], "vout": [ { "amount": 552171057312, "target": { "key": "cc4baeea9e1ccd76d06074d74d8c1b0b78a28a8e6179939b8e8fee925d12e4c5" } } ], "extra": [ 1, 46, 170, 168, 172, 194, 91, 83, 129, 132, 123, 65, 206, 39, 58, 199, 161, 7, 233, 218, 6, 94, 227, 201, 244, 93, 54, 200, 230, 156, 118, 93, 15, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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