Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 617e60b3b60c408721434edbf6386fbac81091fc26b5d43bfca4373d13fd26bd

Tx prefix hash: 55195ce7101dc2867fd4a03ed70cde72f4a64298aa429c3bbe358bc1b2d5758c
Tx public key: 04d890cd64ae87bd2859ece5b1cc2a938f89c19c83081aeed8aa9198da7f4b9d
Timestamp: 1709856274 Timestamp [UCT]: 2024-03-08 00:04:34 Age [y:d:h:m:s]: 01:027:02:37:25
Block: 973473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280347 RingCT/type: yes/0
Extra: 0104d890cd64ae87bd2859ece5b1cc2a938f89c19c83081aeed8aa9198da7f4b9d02110000000246812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c72f5c5725238441d86e7337c8d0d927bff6518f7dbf302ea1d04bf0e37f2a63 0.600000000000 1433408 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": 973483, "vin": [ { "gen": { "height": 973473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c72f5c5725238441d86e7337c8d0d927bff6518f7dbf302ea1d04bf0e37f2a63" } } ], "extra": [ 1, 4, 216, 144, 205, 100, 174, 135, 189, 40, 89, 236, 229, 177, 204, 42, 147, 143, 137, 193, 156, 131, 8, 26, 238, 216, 170, 145, 152, 218, 127, 75, 157, 2, 17, 0, 0, 0, 2, 70, 129, 43, 184, 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