Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855ea36bdee83417813013e45e74e836fee6afe23d716c772251e1dcf61cd29a

Tx prefix hash: f9cb25d5aa9ed944a2714518238f2ad48c2b7b0aff15fff540363a4ae981ff94
Tx public key: 6eef1b7e0f8cf7f5a4b22cd71860e872a7771bac46ba105e07b4b78c69313923
Timestamp: 1700464071 Timestamp [UCT]: 2023-11-20 07:07:51 Age [y:d:h:m:s]: 01:150:00:14:25
Block: 895584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368405 RingCT/type: yes/0
Extra: 016eef1b7e0f8cf7f5a4b22cd71860e872a7771bac46ba105e07b4b78c6931392302110000000433af99f4000000000000000000

1 output(s) for total of 0.661543525000 dcy

stealth address amount amount idx
00: ecf7124cabe2d95b82ae70db346528964fa609f777bd16f3378e9800f101e119 0.661543525000 1351821 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": 895594, "vin": [ { "gen": { "height": 895584 } } ], "vout": [ { "amount": 661543525, "target": { "key": "ecf7124cabe2d95b82ae70db346528964fa609f777bd16f3378e9800f101e119" } } ], "extra": [ 1, 110, 239, 27, 126, 15, 140, 247, 245, 164, 178, 44, 215, 24, 96, 232, 114, 167, 119, 27, 172, 70, 186, 16, 94, 7, 180, 183, 140, 105, 49, 57, 35, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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