Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cebb12b878c19301e456bfb342c4bd86b3bf448bcca592035215d2de06c257e1

Tx prefix hash: fbce89b387255aafcbd3c18207a67cbf38775437fc2502984934bb1697c3323d
Tx public key: ce6970e86ca313e8d6da7b8a06ae562f8d4f4b9e13ee30a87d4a0c6312398418
Timestamp: 1577555800 Timestamp [UCT]: 2019-12-28 17:56:40 Age [y:d:h:m:s]: 05:043:10:30:58
Block: 33676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180871 RingCT/type: yes/0
Extra: 01ce6970e86ca313e8d6da7b8a06ae562f8d4f4b9e13ee30a87d4a0c6312398418021100000004d81c26c0000000000000000000

1 output(s) for total of 474.698969932000 dcy

stealth address amount amount idx
00: 0aeb2b3851e64954e09685b7843c09c52bd712be89f478644539ad98a124ac19 474.698969932000 56475 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": 33686, "vin": [ { "gen": { "height": 33676 } } ], "vout": [ { "amount": 474698969932, "target": { "key": "0aeb2b3851e64954e09685b7843c09c52bd712be89f478644539ad98a124ac19" } } ], "extra": [ 1, 206, 105, 112, 232, 108, 163, 19, 232, 214, 218, 123, 138, 6, 174, 86, 47, 141, 79, 75, 158, 19, 238, 48, 168, 125, 74, 12, 99, 18, 57, 132, 24, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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