Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6087562328ca543e95b3c6e5ae1a8b388b080e00a0df2511276f79698754cade

Tx prefix hash: cb5c105f9a620d25f9a341822058103dee6ba29505ee9b26fc95ac8a4b4a0f0b
Tx public key: bd0dcbc240b323036ea843d8cc65a9712def7418bb07d51862639465cd98d479
Timestamp: 1583753663 Timestamp [UCT]: 2020-03-09 11:34:23 Age [y:d:h:m:s]: 04:361:01:32:40
Block: 79460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152514 RingCT/type: yes/0
Extra: 01bd0dcbc240b323036ea843d8cc65a9712def7418bb07d51862639465cd98d4790211000000286d997e00000000000000000000

1 output(s) for total of 334.747101562000 dcy

stealth address amount amount idx
00: 56ae37eb1249ea7aaaced8e7a80bec3a466405798a5f0f4d1af17852400d61d1 334.747101562000 145314 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": 79470, "vin": [ { "gen": { "height": 79460 } } ], "vout": [ { "amount": 334747101562, "target": { "key": "56ae37eb1249ea7aaaced8e7a80bec3a466405798a5f0f4d1af17852400d61d1" } } ], "extra": [ 1, 189, 13, 203, 194, 64, 179, 35, 3, 110, 168, 67, 216, 204, 101, 169, 113, 45, 239, 116, 24, 187, 7, 213, 24, 98, 99, 148, 101, 205, 152, 212, 121, 2, 17, 0, 0, 0, 40, 109, 153, 126, 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