Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce71237a64ec0c2f60e13e747c31ea5e06923aa45bfde7b7a783850628f7e289

Tx prefix hash: ff1b4fc4262e2456c42d97ec1d5f03b265ac764b6a7a317549d6782e7a95db20
Tx public key: 0d83a7157d44e5727a0e63fb22d3689875e05ace4b625ea9fe5ecc79b70798ab
Timestamp: 1718710968 Timestamp [UCT]: 2024-06-18 11:42:48 Age [y:d:h:m:s]: 00:271:05:33:30
Block: 1046870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193828 RingCT/type: yes/0
Extra: 010d83a7157d44e5727a0e63fb22d3689875e05ace4b625ea9fe5ecc79b70798ab02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974e5397464d1321bba40f33b34e1c5e4d2c3843896a3e873702935f3d6070da 0.600000000000 1516689 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": 1046880, "vin": [ { "gen": { "height": 1046870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974e5397464d1321bba40f33b34e1c5e4d2c3843896a3e873702935f3d6070da" } } ], "extra": [ 1, 13, 131, 167, 21, 125, 68, 229, 114, 122, 14, 99, 251, 34, 211, 104, 152, 117, 224, 90, 206, 75, 98, 94, 169, 254, 94, 204, 121, 183, 7, 152, 171, 2, 17, 0, 0, 0, 6, 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