Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1753ec8e9638d193578f06c8ca30d8990957a75e1f3b5b26fd7ae1a6dfccd28

Tx prefix hash: 46c4787a12a680adc79d6f657738673ab867c0c709e4b7dc98be8a5acd0b599a
Tx public key: 06877fa12d81068b66e58efb1445f66da836ba966f5f1ca02aeba7e5c849936d
Timestamp: 1635362299 Timestamp [UCT]: 2021-10-27 19:18:19 Age [y:d:h:m:s]: 03:201:15:16:23
Block: 361742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 922363 RingCT/type: yes/0
Extra: 0106877fa12d81068b66e58efb1445f66da836ba966f5f1ca02aeba7e5c849936d02110000000242b3953e000000000000000000

1 output(s) for total of 38.850713056000 dcy

stealth address amount amount idx
00: 9ace282cf30d05fe6d9405fd43460661a84c0390ee1c879c0a80bef91d341c04 38.850713056000 735834 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": 361752, "vin": [ { "gen": { "height": 361742 } } ], "vout": [ { "amount": 38850713056, "target": { "key": "9ace282cf30d05fe6d9405fd43460661a84c0390ee1c879c0a80bef91d341c04" } } ], "extra": [ 1, 6, 135, 127, 161, 45, 129, 6, 139, 102, 229, 142, 251, 20, 69, 246, 109, 168, 54, 186, 150, 111, 95, 28, 160, 42, 235, 167, 229, 200, 73, 147, 109, 2, 17, 0, 0, 0, 2, 66, 179, 149, 62, 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